UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

tc Server HORIZON must produce log records containing sufficient information to establish the source of events.


Overview

Finding ID Version Rule ID IA Controls Severity
V-240758 VRAU-TC-000190 SV-240758r879566_rule Medium
Description
After a security incident has occurred, investigators will often review log files to determine what happened. tc Server HORIZON must create a log entry when users access the system, and the system authenticates the users. The logs must contain information about user sessions to include what type of event occurred, when (date and time) events occurred, where within the server the events occurred, the client source of the events, the outcome (success or failure) of the event, the identity of the user/subject/process associated with the event. As a Tomcat derivative, tc Server can be configured with an AccessLogValve. A Valve element represents a component that can be inserted into the request processing pipeline. The pattern attribute of the AccessLogValve controls which data gets logged. The %h parameter will record the remote hostname or IP address that sent the request; i.e. the source of the event.
STIG Date
VMware vRealize Automation 7.x tc Server Security Technical Implementation Guide 2023-10-03

Details

Check Text ( C-43991r674016_chk )
At the command prompt, execute the following command:

tail /storage/log/vmware/horizon/localhost_access_log.YYYY-MM-dd.txt

Note: Substitute the actual date in the file name.

If the source IP of events are not being recorded, this is a finding.
Fix Text (F-43950r674017_fix)
Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml.

Navigate to and locate .

Configure the node with the below.

Note: The "AccessLogValve" should be configured as follows:
directory="logs"
pattern="%h %l %u %t "%r" %s %b"
prefix="localhost_access_log."
suffix=".txt"/>